Add a teaser on uv#4
Conversation
Thank you!Thank you for your pull request 😃 🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}. If you have files that automatically render output (e.g. R Markdown), then you should check for the following:
Rendered Changes🔍 Inspect the changes: https://github.com/esciencecenter-digital-skills/python-intermediate-development/compare/md-outputs..md-outputs-PR-4 The following changes were observed in the rendered markdown documents: What does this mean?If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation. ⏱️ Updated at 2025-10-22 10:51:11 +0000 |
sjvrijn
left a comment
sjvrijn
left a comment
There was a problem hiding this comment.
I think this is fine for now. You're right that since uv [venv|pip] is a drop-in replacement, there is no strict necessity to include it here. Same goes for the associated speed-up, or for having it already installed by the time we reach the packaging section: might be nice, but not needed.
I'm okay with seeing how it goes and perhaps adjusting the material afterwards again based on our experience.
Auto-generated via `{sandpaper}`
Source : 8033634
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2025-10-24 19:42:56 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : 3b39d9f
Branch : main
Author : Francesco Nattino <49899980+fnattino@users.noreply.github.com>
Time : 2025-10-24 19:42:08 +0000
Message : Merge pull request #4 from esciencecenter-digital-skills/uv-teaser-fn
Add a teaser on `uv`
Auto-generated via `{sandpaper}`
Source : 8033634
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2025-10-24 19:42:56 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : 3b39d9f
Branch : main
Author : Francesco Nattino <49899980+fnattino@users.noreply.github.com>
Time : 2025-10-24 19:42:08 +0000
Message : Merge pull request #4 from esciencecenter-digital-skills/uv-teaser-fn
Add a teaser on `uv`
2 participants
At first, I have started on making
uvthe tool used throughout the episode by adapting allvenv/pipcommands (essentially addinguvin front of these) - but then I thought it could still be instructive to use the built-in tools here and point touvas one of the possible options? I mean, commands likeuv venvanduv pipmake much more sense if you have usedvenvandpipbefore. Similarly, you appreciateuv run, after having to activate the environment before calling Python.So, I have ended up only adding a callout on
uv, suggesting it as the tool to try out when in doubt on what to experiment with.What do you think?